System and method for filtering and organizing items based on common elements

ABSTRACT

A system and method for filtering and organizing items in a computer system based on common elements is provided. A graphical user interface includes a plurality of display objects, each display object representing one or more items and a metadata property control corresponding to a metadata property. Selection of the metadata property control causes a list of filter terms to be presented on the display and also may cause a list of check box controls to be presented on the display, each check box control being adjacent to a respective one of the filter terms. The list of filter terms may be presented in a drop down menu. Selection of a check box control causes each item that satisfies the corresponding filter term to be presented on the display. The filters may be dynamically generated based on the properties of the separate items.

CROSS-REFERENCE(S) TO RELATED APPLICATION(S)

This application is a continuation-in part of U.S. patent application Ser. No. 10/440,035, filed May 16, 2003, which is a continuation-in-part of U.S. patent application Ser. No. 10/403,341, filed Mar. 27, 2003, priority from the filing dates of which are hereby claimed under 35 U.S.C. § 120.

FIELD OF THE INVENTION

The present invention relates to systems and methods for viewing items that are stored in a computer memory, and more particularly, to a system and method for filtering and organizing items based on common elements.

BACKGROUND OF THE INVENTION

Present computer file systems have a number of undesirable limitations. One limitation is that users are generally unable to control the structure that they are shown. In other words, when folders are organized, a user must choose a structure, and that structure is then difficult to change. As a specific example, for a “music” folder, a user may choose to organize the music files in an artist/album format, wherein all of the album folders for each artist are grouped into that particular artist's folder, and all of the songs on a particular album are grouped into that album's folder. The artist/album format is not conducive to playing a type of music (e.g., playing two jazz songs from two different artists), or for playing a selection of albums from different artists.

As another issue, a user may have a large number of files which are difficult to organize. Some users implement a rigid sense of placement for the files, and thus create strict hierarchies for them. The management of such files become increasingly complex and difficult as the number of available documents grows, making search and retrieval also difficult. This problem is further exacerbated when additional files are utilized from other locations, such as shared files, etc.

Users also have to deal with files being in different locations, such as on different devices, on other PCs, or online. For example, users can select to listen to their music on the computer (as may be accessible to a music program) or can go online and listen to music from Web sites, however there is a strict division between these two sources. Music coming from different locations is organized differently, and not kept in the same fashion or place. As another example, files stored on a corporate network may inherently be separated from files a user has on a current machine.

Users also have to keep track not only of what file data is stored, but where it is stored. For example, for music files, users are forced to keep copies on various systems and to try to track which music files are located where. This can make files difficult to locate, even when they are locally stored.

It is also sometimes difficult to find and return to files that a user has. A user may find it difficult to recall where and how they stored certain files. Given a set of folders and even a group of similar files, users often find it difficult to quickly find the one that they are looking for. For files stored in a difficult place to find, it is that much more complex to locate. In addition, once users have enough files in a folder, it becomes more difficult to parse the folder quickly, especially if the contents are similar.

It is also sometimes difficult for users to find or return to files on a network. Sharing and publishing files is often hard to do, and it may often be even more difficult to retrieve such a file from someone who makes it available. Users typically have to memorize or map the various sites and names that they need for finding files on a network.

Name spaces may vary, which can cause confusion to the user as to what is “correct.” This is particularly true on a network where there are different naming conventions, limitations, and so on. For example, certain operating systems may require short names with no spaces in order for them to be visible.

Programs also often save files to their own directory or other name spaces, which can make it difficult for users to find their way back to the files. Programs often have default directories and places they save documents. A user often has to search through their hard disk and make guesses about where a file is stored.

Related items are also often stored in separate places. Related files that a user has may be stored on different parts of the hard disk, etc. This problem becomes more common with the developments of digital media services that have multiple content types (e.g., pictures, music, video).

The present invention is directed to providing a system and method that overcome the foregoing and other disadvantages. More specifically, the present invention is directed to a system and method for filtering and organizing items based on common elements.

SUMMARY OF THE INVENTION

A system and method for filtering and organizing items from computer memories based on common elements is provided. In accordance with one aspect of the invention, filters are provided for manipulating the items. The filters are essentially tools for narrowing down a set of items. In one embodiment, the filters are dynamically generated based on the properties of the separate items. For example, for a set of items, the filter mechanism may review the properties, and if the items generally have “authors” as a property, the filter can provide a list of the authors. Then by clicking on a particular author, the items that don't have the author disappear. This allows the user to narrow the contents.

In accordance with another aspect of the invention, a method for filtering items is provided in a computer system having a display and a memory for storing items with metadata properties. Display objects are provided on the display that each represent one or more items. The metadata properties of the items that are represented by the display objects are evaluated. A filter term is provided on the display that corresponds to a metadata property that is shared by a plurality of the items, wherein the selection of the filter term causes the items that are represented on the display to be reduced to those items that share the specified metadata property.

In accordance with another aspect of the invention, a plurality of items is represented on the display, and a filter term is dynamically generated based on the metadata properties of the items. When the filter term is selected, it reduces the items that are represented on the display to those that have the metadata property that corresponds to the filter term.

In accordance with another aspect of the invention, a plurality of items is represented on the display, and a filter area is provided in which a user can select a filter term by selecting a checkbox control. When a checkbox control is selected by the user, the items that are represented on the display are reduced to those that contain the filter term. As the user types the filter term, additional items may be filtered as each new character is added to the filter term.

In accordance with another aspect a graphical user interface is provided including a plurality of display objects, each display object representing one or more items and a property control corresponding to a property that is shared by a plurality of the items. Selection of the property control causes a list of filter terms to be presented on the display. In one aspect the filter terms may be presented in a drop down menu in which each filter has a corresponding checkbox control.

In another aspect of the invention, selection of a first check box control may cause the items that are represented on the display to only include items that satisfy the filter term corresponding to the first check box control. Selection of a second check box control when the first check box control is currently selected causes the items that are represented on the display to include items that satisfy either the first respective filter term corresponding to the first check box control or a second respective filter term corresponding to the second check box control. In other words, the filter terms cause a logical OR operation to be performed on the items in the view.

In still another aspect, the second check box control may be deselected causing the items represented on the display to include only items that satisfy at least one respective filter term corresponding to a currently selected check box control.

In another aspect, selection of a property control may cause a list of arrangement commands to be presented on the display separated from the list of filter terms. The selection of an arrangement command may cause the items to be rearranged on the display. Illustrative arrangement commands including sorting, stacking or group by the property associated with the selected property control.

In yet another aspect, the property control may be a split button. According to this aspect, selection of a first button portion may cause the list of filter terms to be presented on the display and selection of the second button portion may cause the display objects to be sorted by the property.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing aspects and many of the attendant advantages of this invention will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:

FIG. 1 is a block diagram of a general purpose computer system suitable for implementing the present invention;

FIG. 2 is a block diagram of a virtual folder system in accordance with the present invention;

FIG. 3 is a flow diagram illustrative of a routine by which a user provides a query that draws back selected files and folders;

FIG. 4 is a flow diagram illustrative of a routine by which virtual folders are constructed and displayed on the screen in accordance with either a default query or a query from the user;

FIG. 5 is a tree diagram of a folder structure in accordance with a physical folder arrangement on a hard drive;

FIG. 6 is a tree diagram of a virtual folder structure;

FIG. 7 is a tree diagram of the virtual folder structure of FIG. 6, wherein the clients stack is further filtered by contracts and year;

FIG. 8 is a tree diagram of the virtual folder structure of FIG. 7, wherein the contracts of the clients stack are further filtered by year;

FIG. 9 is a tree diagram of the virtual folder structure of FIG. 6, wherein the contracts stack is further filtered by clients and year, of which the clients are still further filtered by year;

FIG. 10 is a diagram illustrative of a screen display showing the stacks of a document library;

FIG. 11 is a diagram illustrative of a screen display showing the documents in the ABC Corp. stack of FIG. 10;

FIG. 12 is a diagram illustrative of a screen display in which a stacking function is selected for the documents of FIG. 11;

FIG. 13 is a diagram illustrative of a screen display in which a “stack by author” parameter is selected for the stacking function of FIG. 12;

FIG. 14 is a diagram illustrative of a screen display in which the files of FIG. 13 have been stacked by author;

FIG. 15 is a diagram illustrative of a screen display in which a stacking function is selected and a “stack by category” option is further selected for restacking the files of FIG. 14;

FIG. 16 is a diagram illustrative of a screen display in which the files of FIG. 14 have been restacked by category;

FIG. 17 is a diagram illustrative of a screen display in which a quick link for showing physical folders is selected;

FIG. 18 is a diagram illustrative of a screen display in which the physical folders are shown which contain the files of the virtual folder stacks of FIG. 17;

FIG. 19 is a flow diagram illustrative of a routine by which a user can directly manipulate virtual folders;

FIG. 20 is a diagram illustrative of a screen display in which a new “West Coast” stack has been added to the stacks of FIG. 10;

FIG. 21 is a diagram illustrative of a screen display in which direct manipulation is used for copying the files from the “ABC Corp.” stack to the “West Coast” stack of FIG. 20;

FIG. 22 is a flow diagram illustrative of a routine for the system dynamically generating new filter terms;

FIG. 23 is a flow diagram illustrative of a routine for the system filtering items based on the selection of a filter term;

FIG. 24 is a diagram illustrative of a screen display in which the stacks of FIG. 10 have been filtered by the term “AB”;

FIG. 25 is a diagram illustrative of a screen display in which the stacks of FIG. 10 have been filtered by the term “ABC”;

FIG. 26 is a diagram illustrative of a screen display in which the filter term “year 2002” is selected for the stacks of FIG. 10;

FIG. 27 is a diagram illustrative of a screen display in which the stacks of FIG. 10 have been filtered by the “year 2002” and the further selection of the filter term “month”;

FIG. 28 is a diagram illustrative of a screen display in which a list is presented for selecting a month for filtering;

FIG. 29 is a diagram illustrative of a screen display wherein the stacks of FIG. 10 have been further filtered by the month of January, and further showing a filter term of “day”;

FIG. 30 is a flow diagram illustrative of a routine for creating a new quick link;

FIG. 31 is a diagram illustrative of a screen display for creating a new quick link called “January Work” based on the filtering of FIG. 29;

FIG. 32 is a diagram illustrative of a screen display in which a quick link of “All Authors” is selected;

FIG. 33 is a diagram illustrative of a screen display in which a list of all of the authors of FIG. 32 is presented;

FIG. 34 is a diagram illustrative of a screen display in which “Author 1” has been selected from the list of FIG. 33 and all of the Author 1's documents are shown;

FIG. 35 is a flow diagram illustrative of a routine for creating a new library;

FIG. 36 is a diagram illustrative of a screen display in which a collection of various available libraries are shown;

FIG. 37 is a flow diagram illustrative of a routine for defining the scope of a virtual folder collection;

FIG. 38 is a block diagram illustrative of the various sources which may form the scope of a virtual folder collection;

FIG. 39 is a flow diagram illustrative of a routine for including non-file items in a virtual folder collection;

FIG. 40 is a diagram illustrative of a screen display showing various non-file items included in a virtual folder;

FIG. 41 is a diagram illustrative of a details view with grouping in a conventional operating system;

FIG. 42A is a diagram illustrative of a property header including property controls in a details view according to aspects of the present invention;

FIG. 42B is a diagram illustrative of a split button property control in a property header in a details view according to aspects of the present invention;

FIG. 42C is a diagram illustrative of an arrange and filter drop down menu of the a property control in a property header in a details view according to aspects of the present invention;

FIG. 42D is a diagram illustrative of part of a filter portion of an arrange and filter drop down menu according to aspects of the present invention;

FIG. 43A is a diagram illustrative of a property header including property controls in a view other than a details view according to aspects of the present invention;

FIG. 43B is a diagram illustrative of an arrange and filter drop down menu of a property control in a property header in a view other than a details view according to aspects of the present invention;

FIG. 43C is a diagram illustrative of a property header where the view has been filtered by one of the property controls in the property header in a view other than a details view according to aspects of the present invention;

FIG. 44 is a diagram illustrative of an arrange and filter drop down menu of an overflow property control in a view according to aspects of the present invention; and

FIG. 45 is a diagram illustrative of a calendar control according to aspects of the present invention.

DETAILED DESCRIPTION

The present invention is directed to folders including virtual or physical folders. Virtual folders utilize the same or similar user interfaces that are currently used for file systems. The virtual folders expose regular files and folders (also known as directories) to users in different views based on their metadata instead of the actual physical underlying file system structure on the disk. Location-independent views are created which allow users to manipulate their files and folders utilizing similar controls as those presently used for managing file systems. In general, this means that users can organize and rearrange their files based on inherent properties in the files themselves, instead of the managing and organization being done as a separate part of the system. The virtual folders may represent files or items from different virtual or physical locations, such as from multiple disk drives within the same computer, between multiple computers, or different network locations, such that one view of files or items can expose files or items sitting at different physical locations. In one embodiment, the different items or files need only be connected via an IP network in order to be included.

The virtual folder modeling is also able to be used for traditionally non-file entities. An application of this is to have a set of user interfaces similar to files and folders (that is, objects and containers) to show traditionally non-file entities. One example of such non-file entities would be e-mails, while another would be contact information from a contact database. In this manner, virtual folders provide for a location-independent, metadata-based view system that works regardless of whether the data being shown is from files or non-file entities. In general, these aspects allow more flexibility in terms of letting users manipulate their files and data, using both common user interface techniques (drag and drop, double-click, etc.) as well as leveraging the rich integration of various data types.

FIG. 1 and the following discussion are intended to provide a brief, general description of a suitable computing environment in which the present invention may be implemented. Although not required, the invention will be described in the general context of computer-executable instructions, such as program modules, being executed by a personal computer. Generally, program modules include routines, programs, characters, components, data structures, etc., that perform particular tasks or implement particular abstract data types. As those skilled in the art will appreciate, the invention may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

With reference to FIG. 1, an exemplary system for implementing the invention includes a general purpose computing device in the form of a conventional personal computer 20, including a processing unit 21, system memory 22, and a system bus 23 that couples various system components including the system memory 22 to the processing unit 21. The system bus 23 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. The system memory includes read-only memory (ROM) 24 and random access memory (RAM) 25. A basic input/output system (BIOS) 26, containing the basic routines that help to transfer information between elements within the personal computer 20, such as during start-up, is stored in ROM 24. The personal computer 20 further includes a hard disk drive 27 for reading from or writing to a hard disk 39, a magnetic disk drive 28 for reading from or writing to a removable magnetic disk 29, and an optical disk drive 30 for reading from or writing to a removable optical disk 31, such as a CD-ROM or other optical media. The hard disk drive 27, magnetic disk drive 28, and optical disk drive 30 are connected to the system bus 23 by a hard disk drive interface 32, a magnetic disk drive interface 33, and an optical drive interface 34, respectively. The drives and their associated computer-readable media provide non-volatile storage of computer-readable instructions, data structures, program modules, and other data for the personal computer 20. Although the exemplary environment described herein employs a hard disk 39, a removable magnetic disk 29, and a removable optical disk 31, it should be appreciated by those skilled in the art that other types of computer-readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, random access memories (RAMs), read-only memories (ROMs), and the like, may also be used in the exemplary operating environment.

A number of program modules may be stored on the hard disk 39, magnetic disk 29, optical disk 31, ROM 24 or RAM 25, including an operating system 35, one or more application programs 36, other program modules 37 and program data 38. A user may enter commands and information into the personal computer 20 through input devices such as a keyboard 40 and pointing device 42. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 21 through a serial port interface 46 that is coupled to the system bus 23, but may also be connected by other interfaces, such as a parallel port, game port or a universal serial bus (USB). A display in the form of a monitor 47 is also connected to the system bus 23 via an interface, such as a video card or adapter 48. One or more speakers 57 may also be connected to the system bus 23 via an interface, such as an audio adapter 56. In addition to the display and speakers, personal computers typically include other peripheral output devices (not shown), such as printers.

The personal computer 20 may operate in a networked environment using logical connections to one or more personal computers, such as a remote computer 49. The remote computer 49 may be another personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the personal computer 20. The logical connections depicted in FIG. 1 include a local area network (LAN) 51 and a wide area network (WAN) 52. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets, and the Internet.

When used in a LAN networking environment, the personal computer 20 is connected to the local area network 51 through a network interface or adapter 53. When used in a WAN networking environment, the personal computer 20 typically includes a modem 54 or other means for establishing communications over the wide area network 52, such as the Internet. The modem 54, which may be internal or external, is connected to the system bus 23 via the serial port interface 46. In a networked environment, program modules depicted relative to the personal computer 20 or portions thereof may be stored in the remote memory storage device. It will be appreciated that the network connections shown are exemplary, and other means of establishing a communications link between the computers may be used.

As implemented on a system of the type illustrated in FIG. 1, the present invention utilizes virtual folders which make it easier for users to perform basic tasks around file manipulation and folder navigation (browsing) and to provide higher level storage capabilities which can be leveraged in new features. The virtual folders expose files and items to users in different views based on their metadata instead of the actual physical underlying file system structure on the disk.

FIG. 2 is a block diagram of a virtual folder system 200 in accordance with the present invention. As will be described in more detail below, the virtual folders allow a user to change the “pivot” which controls the way the data is viewed. As an example, a user could view their music as a flat list of all the songs, which can be grouped by album. Alternatively, the user could switch the view to show only the genres or artists or years, etc. The user can tailor the view to see only the objects suited to the task at hand. This allows an improved browsing experience that negates the need for further navigation through folders (both down and back up). The same lessons and capabilities apply to modeling other data-types not stored as files. Contacts, for example, can be exposed to the user in this way, giving them familiar interface capabilities, as well as richer infrastructure for manipulating them than is provided by a flat address book.

As illustrated in FIG. 2, the virtual folder system 200 includes a folder processor 210, a relational database 230, a virtual folder descriptions database 232, an other shell folders component 234, a folder handler's component 236, and a shell browser and view component 240. The folder processor 210 includes a native handling code component 212, a handler factory component 214, a property writer component 216, a rowset parser component 218, a query builder component 220, an enumerator component 222, and a property factory component 224.

The relational database 230 stores properties about all files in the system. It also stores some items, like contacts (i.e., non-file items), entirely. In general, it stores metadata about the types of files and items that it contains. The relational database 230 receives SQL queries from the query builder 220. The relational database 230 also sends SQL rowsets to the rowset parser component 218, with one row per item column, columns being the item properties.

The virtual folder descriptions database 232 includes the virtual folder descriptions. The virtual folder descriptions database 232 sends data to the query builder component 220, including a list of types to display in the folder, the initial filter, and the physical locations to show results from (the scopes).

With regard to the other shell folders component 234, the folder processor 210 delegates to existing shell folders from many types of items, including all files, for handlers or properties. The other shell folders component 234 sends properties from other folders to the property factory 224. The other shell folders component also sends handlers to the handler factory 214.

The folder handlers component 236 provides code behavior for the items that exist only in the database, like contacts. This is what allows non-file items to behave akin to files. The folder handlers component 236 sends handlers to the handler factory 214.

For the native handling code component 212, the folder processor 210 directly implements certain handlers based on the properties of the items. The native handling code component 212 sends handlers to the handler factory 214. For the native handling code component 212 and the folder handlers component 236, like all namespaces, virtual folders have to provide a set of handlers (context menu, icon, thumbnail, infotip, . . . ) for their items. For most of these (infotip, data object, drag-drop handler, background context menu . . . ) the virtual folder provides a common (native) handler for all the types it holds. However there are others which the author of the type has to provide (context menu on the item itself, writable property store, . . . ). The default handler can also be overridden. Virtual folders reuse this for files and allow non-file items do the same.

The handler factory 214 takes ID lists and produces code behaviors that provide context menus, icons, etc. In general, the folder processor 210 may use native handlers, external handlers, or delegate to other shell folders to get handlers, as described above with respect to the native handling code component 212, the other shell folders component 234, and the folder handlers component 236. The handler factory component 214 sends handlers to the shell browser in view 240, as requested by the view. The handler factory component 214 sends a property handler to the property writer 216.

The property writer 216 converts user intentions such as cut, copy, and paste into property rights to the file or item. A shell browser and view component 240 sends data to the property writer 216, including direct manipulation (cut/copy/paste) or editing of metadata. In general, since virtual folders present an organization based on the properties of an item, operations such as move and copy (drag-drop) become an edit on those properties. For example, moving a document, in a view stacked by author, from Author 1 to Author 2, means changing the author. The property writer component 216 implements this function.

The rowset parser 218 takes database rowsets and stores all item properties into a shell ID list structure. A rowset takes the piecewise definition of the virtual folder and builds a SQL string which can then be issued to the database. The rowset parser component 218 sends ID lists to the enumerator component 222. As described above, the rowset parser component 218 also receives data from the relational database 230, including SQL rowsets, with one row per item, the columns being item properties.

The query builder component 220 builds SQL queries. The query builder component 220 receives data from the enumerator component 222, including new filters from the navigation. The query builder component 220 also receives data from the virtual folder descriptions database 232, including a list of the types to display in the folder, the initial filter, and the physical location to show results from (the scopes). The query builder component 220 sends the SQL queries to the relational database 230.

In general, the query builder component 220 includes a set of rows (in other words a table). This is what running the query yields. The rowset parser component 218 takes each row and using the column names transforms the row into an ID list. An ID list is a well-known shell structure which is used to reference items in a namespace. Doing this allows virtual folders to be just like any other namespace to the rest of the shell. Also caching this data helps keep database access, which can be costly, to a minimum.

The enumerator component 222 operates in response to navigation to a virtual folder. As described above, the enumerator component 222 receives ID lists from the rowset parser component 218, and sends new filters from the navigation to the query builder component 220. The enumerator 222 also sends data to the shell browser and view component 240, including ID lists that are returned to be inserted into the view after a navigation.

The property factory component 224 takes ID lists and property identifiers and returns values for those properties. The property factory component 224 receives data from the handler factory component 214 including the property handler. As described above, the property factory component 224 also receives data from the other shell folders component 234, including properties from other folders. The property factory component 224 also sends data to the shell browser and view component 240, including item properties, as requested by the view.

The shell browser and view component 240 displays the contents of a folder in a window, and handles all the user interaction with the displayed files or items, such as clicking, dragging, and navigating. Thus, the shell browser and view component 240 receives the user actions. The shell browser and view component 240 also gets the data regarding the code behaviors that it needs from the folder, in this case the folder processor 210.

As described above, the virtual folders expose regular files and folders (also known as directories) to users in different views based on their metadata instead of the actual physical underlying file system structure on the disk. Thus, the system is able to take a property that is stored in the database and represent it as a container that is like a folder. Since users are already familiar with working with folders, by presenting the virtual folders in a similar manner, users can adapt to the new system more quickly.

FIG. 3 is a flow diagram illustrative of a routine 300 by which a user provides a query that draws back selected items. At a block 302, the folder processor gets a query from the user. In a block 304, the folder processor passes the query to the relational database. At a block 306, the relational database provides the results back to the folder processor. At block 308, the folder processor provides the results to the user in the form of virtual folders and items.

FIG. 4 is a flow diagram illustrative of a routine 320 by which virtual folders are constructed and displayed on the screen in accordance with either a default query or a query from the user. At a block 322, when a user first opens the virtual folder, a default query is used. This default query is taken from the registry. For example, the default query for a music library could be to show all the songs grouped by album. At a block 324, the folder processor constructs a query object for this query, and then passes this query to the relational database. At a block 326, the relational database generates the results of the query and passes these back to the folder processor as database rows and columns.

At a block 328, the folder processor takes these results and converts them from the rows and columns of data into an enumerator structure, which is used by the folder view to populate the screen with the resulting virtual folders and items for the user to interact upon. At a decision block 330, a user decides whether to change the view (by issuing a different query or “pivot”). For example, a user could issue a “show all artists” pivot. If the user does want to change the view, then the routine returns to block 324 where the folder processor passes this new query to the relational database, and receives back new rows and columns of results, and constructs a new enumerator structure. The process then continues as described above, as the folder view clears and updates, using the enumerator to draw the “artist” objects to the screen.

In one example, album objects are provided that represent containers that users can navigate into. For example, double-clicking the “Beatles” albums will navigate the view to see all of the Beatles' songs. The folder processor issues the “show all Beatles' songs” query to the relational database, which hands back the rows and columns of data for those songs. The folder processor creates an enumerator of all these songs, which then get drawn to the screen.

The user can also choose the view at any point while browsing virtual folders. From the above example, after narrowing down to just show Beatles songs, a user can change the view to only show the songs as albums. The process of changing the view of items into another representation is called “stacking”. This is because the items are conceptually arranged into “stacks” based on that representation. In this case, the songs are rearranged into stacks for each of the various albums. Users can then navigate into one of these stacks, only seeing the songs from that particular album. Again, the user can rearrange the view of these remaining songs into stacks based on a property (e.g., a rating, for example). If the rating property were selected, the songs from that Beatles album would be shown in stacks for a one-, two-, or a three-star rating.

The results of each query depend on which physical or virtual locations are included in the scope. For example, the scope may be made to include only the folders in the user's “my documents” folder. Alternatively, the scope could include all folders on the computer, or even all folders on multiple network connected computers. The user is able to view and change the scope through a scope property sheet. In one example, the scope property sheet could be exposed by right-clicking on the virtual folder and choosing “properties.” The user could add new folders to the scope, or remove folders that were previously added.

One group of users for which virtual folders will provide particular utility is knowledge workers. Virtual folders allow knowledge workers to easily switch between viewing documents by file type, project, case number, author, etc. Since knowledge workers each tend to have a different method for organizing documents, virtual folders can be used to accommodate these different preferences.

FIG. 5 is a tree diagram of a folder structure in accordance with a physical folder arrangement on a hard drive. This physical folder arrangement is based on the traditional implementation of folders, which may be based on NTFS or other existing file systems. Such folders are referred to as physical folders because their structuring is based on the actual physical underlying file system structure on the disk. As will be described in more detail below, this is in contrast to virtual folders, which create location-independent views that allow users to manipulate files and folders in ways that are similar to those currently used for manipulating physical folders.

As illustrated in FIG. 5, a folder 400 is a “my documents” folder. At a first level, the folder 400 includes folders 410, 420, and 430, corresponding to Clients 1, 2, and 3, respectively. At a second level, each of the folders 410, 420, and 430 contain a folder 411, 421, and 431, respectively, which each correspond to the contracts for the selected client. At a third level, each of the folders 411, 421, and 431 contains a folder 412, 422, and 432, respectively, each corresponding to the year 2001. At the third level, each of the folders 411, 421, and 431 also contains a folder 413, 423, and 433, respectively, each corresponding to the year 2002.

It will be appreciated that a number of obstacles are presented to a user who wishes to navigate a physical folder file structure such as that illustrated in FIG. 5. For example, if the user wishes to work with all of the contracts that the user has produced, the user will first need to navigate to the folder 411 to work with the contracts for Client 1, and then will have to renavigate to the folder 421 to reach the contracts for Client 2, and will again have to renavigate to the folder 431 for the contracts for Client 3. This arrangement makes it difficult for the user to access all of the contracts, and in general prevents simultaneous viewing and manipulation of all of the contracts. Similarly, if the user wishes to view all of the contracts produced in the year 2001, the user will have to navigate and renavigate to the folders 412, 422, and 432, respectively. As will be described in more detail below, the virtual folders of the present invention provide an improved file system structure.

FIG. 6 is a tree diagram of a virtual folder structure. As will be described in more detail below, virtual folders create location-independent views that allow users to manipulate their files and folders in convenient ways. As shown in FIG. 6, the virtual folders are represented as stacks. A virtual folder 500 is an “all items” folder. At a first level, the virtual folder 500 contains virtual folders 510, 520, and 530, corresponding to clients, contracts, and year, respectively. As will be described in more detail below, this structure allows a user to access files according to a desired parameter.

FIG. 7 is a tree diagram of the virtual folder structure of FIG. 6, wherein at a second level, the virtual folder 510 further includes virtual folders 511 and 512, which correspond to contracts and year, respectively. In other words, the clients stack of virtual folder 510 is further filtered by contracts and year. The process for determining which files and items are contained in each of the virtual folders will be described in more detail below.

FIG. 8 is a tree diagram of the virtual folder structure of FIG. 7, wherein at a third level, the virtual folder 511 contains a virtual folder 513, which corresponds to a year. In other words, the contracts stack of virtual folder 511 is further filtered by year. While the virtual folder structure for the virtual folders 510, 511, and 513 have been structured according to clients, contracts, and year, it will be appreciated that the virtual folders allow for other structuring sequences to occur, as will be described in more detail below with reference to FIG. 9.

FIG. 9 is a tree diagram of the virtual folder structure of FIG. 6, wherein at a second level, the virtual folder 520 has been further filtered into virtual folders 521 and 522, corresponding to clients and year. At a third level, the virtual folder 521 has further been filtered to a virtual folder 523, corresponding to a year. The contrast between the organizational structures of FIGS. 8 and 9 helps illustrate the flexibility of the virtual folder system. In other words, in a virtual folder system, a user is able to navigate the virtual folders according to desired parameters, as opposed to being dependent on the location-dependent views of a physical file structure such as that illustrated in FIG. 5.

FIG. 10 is a diagram illustrative of a screen display 600 showing the stacks of a document library. As noted above, stacks can be used to represent a type of virtual folder. As will be described in more detail below, the screen display 600 includes quick link elements 610-613, filter elements 620-626, activity elements 630-633, information and control elements 640-645, and virtual folder stacks 651-655.

The quick link elements include an “all categories” quick link 610, on “all authors” quick link 611, a “January work” quick link 612, and a selection for displaying additional quick links 613. As will be described in more detail below, quick links can be selected by a user to perform desired navigations of the virtual folders. Quick links may be provided by the system, and some quick links may be created and saved by a user.

The filter elements include a “filter by” indicator 620, an entry blank 621, a “by date” indicator 622, a “year” selector 623, a “pick an author” selector 624, a “pick a category” selector 625, and a “more filters” selector 626. The “filter by” indicator 620 directs a user to the fact that the items below can be used to filter the virtual folders or items. The entry blank 621 provides an area in which a user can type a desired new filter term. The “by date” indicator 622 directs a user to the fact that by selecting a date from the “year” selector 623, the virtual folders or items can be filtered by the selected year. The “pick an author” selector 624 allows a user to filter according to a specific author. The “pick a category” selector 625 allows a user to filter according to a selected category. The “more filters” selector 626 allows a user to pull up additional filters on the display.

The activity selectors include a “create a new category” selector 630, “activity” selectors 631 and 632, and a “more activities” selector 633. As will be described in more detail below, the activities that are presented may be for generally desirable functions, or may more specifically be directed to activities useful for the type of virtual folders that are currently being displayed. For example, the “create a new category” selector 630 can be selected by the user to create a new category which will be represented by a new stack.

As noted above, the activity selectors 631 and 632 may be more specifically directed to the type of folders or items that are being displayed. For example, the present display is of a document library, for which the “activity” selectors 631 and 632 may be directed to activities specifically tailored for documents, such as editing or creating attachments. If the present library had been a photo library, the “activity” selector 631 and 632 could be for activities specifically directed to photos, such as forming photo albums or sharing photos with other users.

The information and control elements include information line 640 and information line (address bar) 641, a control line 642, a backspace control 643, and information lines 644 and 645. The information line 640 and address bar 641 provide information as to the current navigation of the virtual folders or items. In the present example, the information line 640 indicates that the current navigation is to a document library, while the address bar 641 indicates the more complete navigation, showing that the document library is within the storage area. The control line 642 provides a number of standard controls, and the backspace button 643 allows a user to back up through a navigation. The information line 644 provides numerical information about the contents of the present navigation. In the present example, the information line 644 indicates that there are 41 items which take up 100 MB in the stacks of the document library. The information line 645 is available to provide additional information, such as additional information about a file that is selected.

The stacks of the document library include an “ABC Corp.” stack 651, a “backups stack” 652, a “business plans” stack 653, an “XYZ Corp.” stack 654, and a “marketing reports” stack 655. The numbers on top of each of the stacks indicate how many items are in each stack. For example, the “ABC Corp.” stack 651 is shown to include 8 items. The total number of items of the stacks adds up to the number of items indicated in the information line 644, which as described above is 41 in the present example. A selection box SB is provided which can be utilized by a user to select a desired item. The selection of the “ABC Corp.” stack 651 yields a view of the items of that stack, as will be described below with respect to FIG. 11.

FIG. 11 is a diagram illustrative of a screen display showing the items in the “ABC Corp.” stack 651 of FIG. 10. It should be noted that the information line 640 and address bar 641 now indicate that the present navigation is showing the “ABC Corp.” stack. The “ABC Corp.” stack 651 is shown to include 8 documents 751-758, corresponding to documents 1-8, respectively. The information line 644 correspondingly indicates that there are 8 items which take up 20 MB of memory. Documents of FIG. 11 may be further arranged into stacks within the ABC Corp. stack. In other words, within the virtual folder represented by the ABC Corp. stack 651, additional virtual folders may be organized to hold the documents, as will be described below with respect to FIGS. 12-16.

FIG. 12 is a diagram illustrative of a screen display in which a stacking function is selected for the documents of FIG. 11. As shown in FIG. 12, the user is able to pull up a function box 760. The function box 760 includes a “view” selection 761, an “arrange icons by” selection 762, a “stacks” selection 763, a “refresh” selection 764, an “open containing folders” selection 765, a “cut” selection 766, a “copy” selection 767, an “undo” selection 768, a “new” selection 769, and a “properties” selection 770. The selection box SB is shown to be around the “stacks” selection 763.

FIG. 13 is a diagram illustrative of a screen display in which a “stack by author” parameter is selected for the stacking function of FIG. 12. As shown in FIG. 13, a box 780 is displayed which presents various stacking options. The stacking options include an “unstack” option 781, a “stack by category” option 782, a “stack by author” option 783, and a “stack by a user” option 784. The selection box SB is shown to be around the “stack by author” option 783.

FIG. 14 is a diagram illustrative of a screen display in which the files of FIG. 13 have been stacked by author. As shown in FIG. 14, stacks 791 and 792 correspond to authors Bob and Lisa, respectively. As indicated by the numbers on top of each of the stacks, the Bob stack 791 includes two items, while the Lisa stack 792 includes five items. The item 758 (corresponding to document 8) did not have an author, and so is not included in an “author” stack. The stacks 791 and 792 illustrate that stacks may be organized at multiple levels, such as within the “ABC Corp.” stack 651. Thus, the virtual folders may be formed at multiple levels, such as the “Lisa” stack 792 being within the “ABC Corp.” stack 651 which is within the document library.

FIG. 15 is a diagram illustrative of a screen display in which a “stack by category” option is further selected for restacking the files of FIG. 14. As shown in FIG. 15, the selection box SB is around the “stack by category” option 782. Since some of the items are already stacked in the stacks 791 and 792, the selection of the “stack by category” option 782 will restack the items, as will be described in more detail below with reference to FIG. 16.

FIG. 16 is a diagram illustrative of a screen display in which the files of FIG. 14 are restacked by category. As shown in FIG. 16, the stacks 793 and 794 correspond to the “XYZ Corp.” and “marketing reports” categories, respectively. The items 751 and 752, corresponding to documents 1 and 2, were not designated for any additional categories, and thus did not fall into any of the other category stacks.

FIG. 17 is a diagram illustrative of a screen display in which a quick link for physical folders is selected. The selection box SB is shown to be around the “all folders” quick link 616. As will be described in more detail below with respect to FIG. 18, the “all folders” quick link 616 provides for switching to a view of physical folders.

FIG. 18 is a diagram illustrative of a screen display showing physical folders. The physical folders that are shown contain the files of the virtual folder stacks of FIG. 17. In other words, the items contained within the stacks 651-655 of FIG. 17 are also contained in certain physical folders in the system. These are shown in FIG. 18 as a “My Documents” folder 851 that is located on the present computer, a “Desktop” folder 852 that is located on the present computer, a “Foo” folder 853 that is located on the hard drive C:, a “My Files” folder 854 that is located on a server, an “External Drive” folder 855 that is located on an external drive, a “My Documents” folder 856 that is located on another computer, and a “Desktop” folder 857 that is located on another computer.

As shown in FIG. 18, a user is able to switch from the virtual files representation of FIG. 17 to the physical file representation of FIG. 18. This allows a user to toggle between virtual file representations and physical file representations, depending on which is desired for a current task. The different locations of the physical folders 851-857 also illustrate that the scope of the virtual file system may be relatively broad, as will be described in more detail below.

FIG. 19 is a flow diagram illustrative of a routine 880 by which a user can directly manipulate virtual folders. As will be described in more detail below, the mechanisms that are provided for manipulating the virtual folders are similar to those that are currently used for manipulating regular folders (e.g., clicking and dragging, copying, pasting, etc.). As shown in FIG. 19, at a block 882, the system provides defined actions that the user can perform for direct manipulation of the virtual folders that are represented as display objects. At a block 884, the user performs a defined action. As noted above, one example of this might be a user clicking and dragging a virtual folder to copy its contents to another virtual folder. At a block 886, the virtual folder and/or contents are manipulated as directed by the action performed by the user.

FIG. 20 is a diagram illustrative of a screen display in which a new West Coast stack 656 has been added to the stacks of FIG. 10. The West Coast stack 656 was formed by a user creating a new category of “West Coast.” Upon its initial creation, the new West Coast stack 656 would be empty and have zero items. In the embodiment of FIG. 20, two items have been added to the West Coast stack 656. One method for adding items to a stack is to select a particular item, and either modify or add additional categories to the category metadata for the item, such as adding the category “West Coast” to two items as was done in the embodiment of FIG. 20. This process illustrates that the category data is a metadata property for an item that is a type of ad-hoc property. In other words, a property of this type does not have any implicit meaning, and can be assigned an arbitrary value by the user. For example, the category “property” can have any value whereas the “author” property should be the name of a person. As will be described in more detail below with reference to FIG. 21, items may also be clicked and dragged to be copied from other stacks to the West Coast stack 656 (in which case the categories of the items are automatically updated to include “West Coast”). In this regard, FIG. 20 shows that the selection box SB is around the ABC Corp. stack 651, in preparation for its contents being copied.

FIG. 21 is a diagram illustrative of a screen display in which direct manipulation is used for copying the files from the ABC Corp. stack 651 to the West Coast stack 656. In other words, as shown in FIG. 20, the user selected the ABC Corp. stack 651, and then as shown in FIG. 21 the user has clicked and dragged the stack to be copied to the West Coast stack 656. Thus, the West Coast stack 656 which had two items in FIG. 20, is now shown to include a total of ten items, including the additional eight items from the ABC Corp. stack 651. When the items from the ABC Corp. stack 651 were copied to the West Coast stack 656, this was accomplished by modifying the category descriptions of the eight items to also include the “West Coast” category in addition to including the original “ABC Corp.” category. This illustrates one type of direct manipulation that may be performed.

Another example of direct manipulation is right clicking an item and selecting delete. In one embodiment, when a deleting function is selected by a user, the user is queried whether the item should be deleted all together, or simply removed from the present virtual folder. If the item is just to be removed from a present virtual folder category stack as noted above, this can be accomplished by removing the desired category from the metadata for the item. In other words, if one of the items that had been copied from the ABC Corp. stack 651 to the West Coast stack 656 was then to be removed from the West Coast stack 656, this could be accomplished by modifying the category data for the particular file to no longer include the “West Coast” category.

FIG. 22 is a flow diagram illustrative of a routine 900 for the system dynamically generating new filter terms. Filter terms are utilized for manipulating the virtual folders. The filtering terms are essentially utilized as a set of tools for narrowing down a set of items. In one embodiment, filters consist of metadata categories and their values (presented to the user in the user interface as clickable links or drop-down menus). Such an illustrative embodiment is described in connection with FIGS. 42 and 43 below. The user clicks on a filter term in order to filter down the current results set of items on the display.

FIG. 22 illustrates how filters may be dynamically generated. As shown in FIG. 22, at a block 902, the properties (from the metadata) of the items in a collection on the present display are reviewed. In a block 904, proposed filter terms are dynamically generated based on common properties of the items in the display. At a block 906, the proposed filter terms are presented to the user for possible selection for filtering items. As an example of this process, the system may review the properties of a set of items, and if the items generally have “Authors” as a property, the filter can provide a list of the authors to filter by. Then, by clicking on a particular Author, the items that don't have that Author are removed from the set on the display. This filtering process provides the user with a mechanism for narrowing the set of items on the display.

FIG. 23 is a flow diagram illustrative of a routine 920 for the system filtering items based on the selection of a filter term. At a block 922, the user either enters a new filter term or else selects one of the filter terms that have been presented by the system. As noted above, the filter terms may be dynamically generated by the system, or they may be preset. At a block 924, the items from the collection on the display are evaluated with regard to whether their selected properties match the filter term. For example, if the filter term is for items that were authored by “Bob,” then the items are evaluated in accordance with whether their author property includes “Bob”. At block 926, the items for which the selected properties do not match the filter term are removed from the collection on the display.

FIGS. 24-29 generally illustrate how the filtering process appears on the screen display. As will be described below with reference to FIGS. 24-29, in one embodiment, the filtering may generally operate according to the following process. After the user clicks on a filter value, the items outside the filter range are animated off the screen. The animation is generally designed to make it obvious that items are being removed and that no new items are being added. The back button 643 may be selected by a user so as to undo the filter operations. In one embodiment, a navigation stack is created which contains the sequential filter actions, which is utilized to undo each of the filter actions when the back button 643 is selected. Each time a filter value is selected, the information area 640 and address bar 641 are updated to indicate the current filter value. In one embodiment, after a filter value is selected, a user is provided an option for saving a new quick link to the current filter navigation, as will be described in more detail below with respect to FIG. 30 or creating an autolist. As filter values are selected, the filter controls may be updated to be appropriate for the items remaining in the view.

FIG. 24 is a diagram illustrative of a screen display in which the stacks of FIG. 10 have been filtered by the term “AB”. As shown, in the filter area 621, the term “AB” has been typed by a user. The information line 640 and address bar 641 indicate that the items in the display are now those that have been filtered by the term “AB”. As shown, the ABC Corp. stack 651 still contains eight items, while the Backups stack 652 now contains three items, and the XYZ Corp. stack 654 also contains three items. The information line 644 thus indicates that there are a total of 14 items, taking up a total of 35 MB of memory.

FIG. 25 is a diagram illustrative of a screen display in which the stacks of FIG. 10 have been filtered by the term “ABC”. With regard to the filter term “AB” of FIG. 24, the user has simply typed the additional letter “C” to make the total filter term “ABC”. As shown in FIG. 25, the information line 640 and address bar 641 now indicate that the items on the display are those that contain the term “ABC”. The ABC Corp. stack 651 is still shown to contain eight items, while the Backups stack 652 now contains only two items. The XYZ Corp. stack 654 has disappeared because none of its contents matched the “ABC” filter. The information line 644 now indicates that there are a total of 10 items in the stacks on the display, which take up a total of 25 MB of memory. FIGS. 24 and 25 thus provide examples of how a user may enter new filter terms, and how those filter terms are then used to filter the items that are shown on the display.

The back button 643 may be utilized by a user to back through the filtering process. As described above with respect to FIG. 10, the back button 643 allows a user to back up through a navigation. With regard to the examples of FIGS. 24 and 25, after filtering by the term “ABC” in FIG. 25, a user could select the back button 643 so as to back up one step of the filtering process, which would return to the state of FIG. 24. Alternatively, in another embodiment, the back button 643 may clear out the entire filter term, and may thus return to the state before that filtering occurred. In this case, by pressing the back button 643 in FIG. 25, a user would return to the state of FIG. 10.

In one embodiment, in addition to the back button, an additional means is provided for a user to back up in or otherwise modify the filtering navigation. This additional means involves allowing the user to directly access and modify the address bar 641, which correspondingly changes the filter navigation. In other words, by directly accessing and modifying the address bar 641, the user can remove one or more of the applied filters, or modify the values for any of the applied filters. This feature is described in greater detail in U.S. patent application Ser. No. 10/420,040, filed Apr. 17, 2003, which is commonly assigned and hereby incorporated by reference in its entirety.

A timer may also be utilized in conjunction with a user typing in filter terms such as those shown in FIGS. 24 and 25. The timer is used to monitor for a pause in the typing by the user. After a selected interval of no typing, the filter is applied. For example, in the state of FIG. 24, a user has typed the filter term “AB”, with no significant time lag between the “A” and the “B.” After typing the term “AB”, the user pauses, thus producing the state shown in FIG. 24, where the filter term “AB” is applied. Sometime later, the user adds the letter “C” to complete the filter term “ABC”, and then pauses again, at which point the filter term “ABC” is applied as illustrated in FIG. 25.

In one embodiment, after a user has typed a filter term in the filter area 621, and then chooses another filter or navigation, the navigation state is updated, and the filter term in the filter area 621 is made to be empty again. In addition, as will be described in more detail below with reference to FIGS. 26-29, other filter controls may be updated based on the selection of certain filter terms.

FIG. 26 is a diagram illustrative of a screen display in which the system provided filter term “year 2002” is selected. As noted above, under the by date indicator 622, the year selections 623 include the years 2000, 2001, or 2002. The selection box SB is shown to be around the year 2002, indicating that the user is selecting that as the desired filter term.

FIG. 27 is a diagram illustrative of a screen display in which the filter term “2002” has been applied. Also shown is the further selection of the “pick a month” selector 623A. As shown in FIG. 27, after applying the filter term “2002”, the number of items in the stacks is reduced. More specifically, the ABC Corp. stack 651 now contains six items, the Backups stack 652 now contains eight items, the Business Plans stack 653 now contains three items, and the XYZ Corp. stack 654 now contains five items. The information line 644 now indicates a total of 22 items, taking up a total of 50 MB of memory. The information line 640 and address bar 641 now indicate that the items shown on the display are those that have been filtered to contain the filter term “2002”.

FIG. 28 is a diagram illustrative of a screen display in which a list is presented for selecting a month for filtering. A box 950 is provided which includes the list of the months. The box 950 has been provided on the display due to the user selecting the “pick a month” selector 623A. The selection box SB is shown to be around the month of January.

FIG. 29 is a diagram illustrative of a screen display wherein the stacks of FIG. 28 have been further filtered by the month of January, and further showing a filter term of “day”. As shown in FIG. 29, the information line 640 and address bar 641 now indicate that the items on the display are those that have been filtered by the term “January”. The Backups stack 652 is now shown to contain two items, while the Business Plans stack 653 is also shown to contain two items. The information line 644 indicates that there are a total of four items on the display, which take up a total of 10 MB of memory. A “pick a day” selector 623B is provided, should the user wish to further filter the results to a specific day. An illustrative calendar control where a day or range of dates may be selected is shown in FIG. 45.

As described above with respect to FIGS. 24-29, filter terms may be presented by the system, or typed by a user. Once a filter term is selected, the remaining filter terms that are presented may be updated (e.g., after the year “2002” is selected in FIG. 26, in FIG. 27 the options for selecting a year are no longer presented and instead a “pick a month” option is provided). As noted above, the back button 643 may be selected by a user to back through the filtering process. For example, after the month of “January” has been selected in FIG. 29, the user may select the back button 643 to back up the filtering process to the year “2002”, as illustrated in FIG. 27. The filter menu may also include a “stack by” function, which would work similarly to the stack by function described above with respect to FIGS. 15 and 16. For example, a “file type” filter could have choices for “Excel”, “PowerPoint”, “Word”, and also “Stack by file type”. Choosing the “stack by” function changes the view to show stacks for the various file types.

In general, the filters may be configured to apply to different properties of the files or items. In one embodiment, the filters may be classified according to different types, such as: alphabet index; discrete values; dates; and numerical ranges. Example properties for the alphabet index may include file name, author, artist, contact friendly name, owner, document author, document title, document subject, and description. Example properties for the discrete values may include location, file type (application name), genre, track, decade (for music), rating (for music), bit rate, protected, document category, document page count, document comments, camera model, dimensions, product name, product version, image X, image Y, and document created time. Example properties for the dates may include last accessed, last modified, created on, taken on (for pictures). An example property for the numerical range may be file size.

It will be appreciated that the filters described above with respect to FIGS. 24-29 allow users to reduce a list of items to find a particular item that is of interest. As a specific example, according to the processes described above, a user could narrow a current list of documents to only show Microsoft Word files, authored by a particular person and edited in the last week. This functionality allows a user to find a particular item in a list of many, and helps the user avoid having to manually scan each item in the list.

FIG. 30 is a flow diagram illustrative of a routine 940 for creating a new quick link. As will be described in more detail below, quick links are predefined links that can be clicked on by a user to create user selected views of the sets of items. In one embodiment, a quick link may be thought of as a type of pivot. Quick links provide a mechanism for retrieving a virtual folder. Clicking a quick link can take a user to a desired folder (in the same way that clicking a “favorites” may take a user to a Web site). The quick links can be predefined by the system, or can be set by a user. For example, clicking on “all authors” could return a view stacked by authors. Clicking on “all documents” may return a flat view for all of the documents for all of the storage areas. Users can also create their own quick links.

As shown in FIG. 30, at a block 942, a user makes a selection on the display to indicate that a new quick link should be formed from the present filter term or navigation. At a block 944, the user provides a new name for the new quick link. At a block 946, the new quick link is saved and the new quick link name is provided in the quick link section on the display.

FIG. 31 is a diagram illustrative of a screen display for creating a new quick link called “January Work” based on the filtering of FIG. 29. As described above, in FIG. 29, the stacks have been filtered by the month of January. In FIG. 31, the user has indicated that the filtering of FIG. 29 should be saved as a new quick link, and has named the new quick link “January work”. Thus, the new January work quick link 612 is shown in the quick links section of the display. With regard to forming new quick links, the user is generally provided with an option such as “save this collection as a quick link”.

FIG. 32 is a diagram illustrative of a screen display in which a quick link of “All Authors” is selected. As shown in FIG. 32, the selection box SB is shown around the All Authors selection 611. Other examples of collections that might be accessible by quick links include “all authors”, “recent documents”, “all documents I've shared”, “all documents I've authored”, “all documents not authored by me”, “desktop”, and “all types”.

FIG. 33 is a diagram illustrative of a screen display in which a list of all of the authors of the items of FIG. 32 is presented. As shown in FIG. 33, an information line 950 is provided, which indicates columns for showing the name of an item, the author, the modified date, the type, the size, and the location of an item. A list of Authors 951-954 is shown, corresponding to Authors 1-4, respectively.

FIG. 34 is a diagram illustrative of a screen display in which “Author 1” has been selected from the list of FIG. 33. The Author 1's documents include documents 951A and 951B, corresponding to documents 1 and 2, respectively. The document 951A is shown to have been authored by Author 1, was modified on 11 Jul. 2001, is a Microsoft Excel file, takes up 282 Kb of memory, and was obtained from the location \\server1\folder2. The document 951B is shown to have been authored by Author 1, was modified on 22 Dec. 2002, is a Microsoft Word file, takes up 206 kilobytes of memory, and is physically stored in the location My Documents\folder1. The locations of the documents 951A and 951B also illustrate that the virtual folders of the present invention may contain items from different physical locations, as will be described in more detail below.

FIG. 35 is a flow diagram illustrative of a routine 960 for creating a new library. One example of a library is the documents library described above with reference to FIG. 10. In general, libraries consist of large groups of usable types of files that can be associated together. For example, photos may be one library, music may be another, and documents may be another. Libraries may provide tools and activities that are related to the particular types of items. For example, in the photo library, there may be tools and filters that relate to manipulating photos, such as for creating slide shows or sharing pictures. As shown in FIG. 35, at a block 962, a new library is created which is to include items with selected characteristics. At a block 964, the selected items are grouped into the library. At a block 966, the tools and/or activities related to the selected characteristics of the items or to other desired functions are provided.

FIG. 36 is a diagram illustrative of a screen display in which a collection of available libraries are shown. As shown in FIG. 36, the libraries include a documents library 971, a photos and video library 972, a music library 973, a messages library 974, a contacts library 975, and a TV and movies library 976, as well as an all items library 977. The all items library 977 is shown to include 275 items, which is the total number of items from all of the other libraries combined. The information line 644 indicates a total of 275 items, which take up a total of 700 MB of memory. It should be noted that the documents library 971 is the library that was described above with respect to FIG. 10.

FIG. 37 is a flow diagram illustrative of a routine 990 for defining the scope of a virtual folder or auto list collection. As will be described in more detail below, a virtual folder system is able to represent items from multiple physical locations (e.g., different hard drives, different computers, different networks locations, etc.) so that to a user, all of the items are readily accessible. For example, a user can be presented with music files from multiple physical locations on a single display, and manipulate the files all at once.

As shown in FIG. 37, at a block 992, a scope is defined for the physical locations from which items are to be drawn. At a block 994, in response to a query, the items are drawn from the physical locations as defined in the scope. At a block 996, all of the items drawn by the query are presented on a single display.

FIG. 38 is a block diagram illustrative of the various sources which may form the scope of a virtual folder collection. As shown in FIG. 38, the system 1000 may include a present computer 1010, an additional computer 1020, external and removable storage 1030, and locations on a network 1040. The overall scope 1001 is described as including all of the physical locations from which a user's items are drawn to create collections. The scope may be set and modified by a user. As noted above, other figures have illustrated that items may come from different physical locations, such as FIG. 34 showing different documents coming from a server and a My Documents folder on a present computer, and in FIG. 18 showing physical folders that are physically stored in multiple locations.

FIG. 39 is a flow diagram illustrative of a routine 1080 for including non-file items in a virtual folder collection. Non-file items are contrasted with file items that are typically located in a physical file storage. Examples of non-file items would be things like e-mails, or contacts. As shown in FIG. 39, at a block 1082 a database is utilized to include non-file items along with file items that may be searched by a query. At a block 1084, in response to a query, both non-file items and file items are drawn to match the query. At a block 1086, both the non-file items and the file items that matched the query are presented on the display.

FIG. 40 is a diagram illustrative of a screen display showing various non-file items. As shown in FIG. 40, the items have been filtered to those that include “John”. The items are shown to include a contact item 1101, an e-mail item 1102, and document items 1103 and 1104. The contact item 1101 and e-mail item 1102 are non-file items. The present system allows such non-file items to be included with regular file items, such that they can be organized and manipulated as desired by a user. As was described above with respect to FIG. 2, such non-file items may be contained entirely within the relational database 230, which otherwise includes information about the properties of files.

In another aspect of the invention, a graphical user interface is provided where a different type of filter control is implemented. According to this aspect, metadata property controls corresponding to properties that are shared by a plurality of the items are provided in the listview mode. It will be appreciated that the description above applies to the following discussion where applicable and without specific reference thereto.

In the Microsoft Windows XP brand operating system by Microsoft Corporation of Redmond, Wash., users are provided with different views for viewing a list of folders and files that are currently identified in the tree structure. The views include a details view, icon view, thumbnail view, list view and tiles view. The objects identified in these views can be sorted or grouped by a number of different metadata properties. FIG. 41 provides an illustrative screen shot of details view in the Windows XP brand operating system. In details view, each row corresponds to a particular object and each column corresponds to a particular property of the object. The properties may be listed in any desired order. In this example, the properties identified from left to right include Name, Size, Date Modified, Date Created, Date Accessed, Author and Type. The objects and their associated information have been divided into two separate groups according to Type—HTML Document and Microsoft Word Document. The “Show in Groups” command is accessible by drilling down to the “Arrange Icons By” drop down menu, via the “View” drop down menu at the top of the screen. Selection of a property, such as author, would causes the objects to be regrouped according to author. If grouping was not activated, selection of a property causes the objects to be sorted by the selected property.

Aspects of the present invention build upon some of the core functionality of the user interface in the Windows XP brand operating system. Certain aspects of the invention provide and arrange and filter control that enables a user to filter a view using properties shared by a plurality of items. The filter control in some aspects allows a user to easily add, change or remove a filter term from an address bar, such as address bar 641 shown previously in, for example, FIG. 24. In one implementation applying the filter control, a user may filter a view of display objects by a disjunction, “ORing” multiple values of a single property (e.g., author=“Bill” or “Bob”). In other aspects applying the filter control, a user can sort, group or stack a view of display objects by a property.

According to aspects of the invention, a property header appears as a set of labels along the top of the listview in each of the view modes. The view modes may include any view of the physical or virtual files including the icons view, details view, list view, tiles view and thumbnail view. Each of the properties in the property header functions as a property control and may be invoked by user selection, such as by clicking on the property control to access associated control functionality. There will likely be numerous properties that may be available to the user. As such, it may be practical to display a relevant subset of properties that is most useful to the user. In this regard, the set of properties displayed in the display header may be customizable by the user, may be part of a default template or may be a function of the query on the address bar. One way to select a set of properties to be displayed is on an individual shell folder (i.e., page) basis, so that for each virtual folder (autolist), list, file folder, etc. where the set of properties may be customized by default. For example, for a virtual folder called “Recent Documents” that shows all documents viewed recently, the “Date Last Accessed” property would be useful, whereas in other virtual folders, it may not be useful. Also, properties may be reordered within the property header or removed by, for example, dragging and dropping.

FIG. 42A shows a property header 4200 for a details view according to an illustrative implementation of the invention and FIG. 43A shows a property header 4300 for other listview modes such as a tiles view or thumbnails view. As can be seen the primary difference between the property headers in FIGS. 42A and 43A is that the individual property controls in the header 4200 in details view map to the column sizes in the details view, whereas the individual property controls in the header 4300 occupy only the space required to fit the property name. Below the property header is an area of the listview mode (not shown) in which the display objects (e.g., physical files and folders, virtual files and folders) are displayed.

Each property control in the respective header may include a split button divided into a main portion 4210 and a split portion 4212 as shown in details view in FIG. 42B and the other listview modes in FIG. 43B. The split button state may be revealed to the user when she positions the cursor 4220 over a portion of the property control or in the property header 4200, or may be revealed when the property control is initially displayed.

Positioning the cursor 4220 over the main portion 4210 of the property control and selecting (e.g., clicking) causes the display objects to be sorted in accordance with the property associated with property control. In the example shown in FIG. 42B, the property is “Type”, selection of the main portion 4210 of the property control would cause the display objects to be sorted alphabetically. Alternatively, all physical folders may be displayed, followed by all Microsoft Excel documents, followed by all Microsoft PowerPoint documents, followed by all Microsoft Word documents, followed by all virtual folders (autolists) etc. When the display objects are sorted by a property, the property control may provide a visual indication that the display objects have been sorted by the property. For example, the property control may take on a visual appearance as being a depressed button or other appearance differentiating it from the other property controls. If prior to sorting by “Type”, the display objects were sorted by another property such as “Date”, that property would become the secondary sort term, such that within the document type the display objects would be secondarily sorted by date.

As shown in FIGS. 42C and 43B, positioning the cursor 4220 over the split portion 4212 of the property control and selecting causes an arrange and filter dropdown menu for the property corresponding to the property control to be presented. The arrange and filter drop down menu provides various controls which allow a user to group, stack or filter the view of display objects by the property corresponding to the property control. The arrange and filter drop down menu includes an arrangement portion 4230 including a list of arrangement commands and a filter portion 4235 including a list of filter terms. The two lists may be separated by a visual divider as shown in FIGS. 42C and 43B.

In the example of FIGS. 42C and 43B, the filter terms correspond to various “Type” properties of the items. The set of specific filters provided in the filter portion 4235 is the subset of possible filter terms for which at least one item in the view satisfies the filter term. For example, if one of the display objects in the view were a photo with “vacation” as a keyword, then “vacation” would appear in the arrange and filter drop down menu for the keyword property control corresponding to the keyword property. It will be appreciated that all filter terms may not fit into the arrange and filter drop down menu. As shown, in FIGS. 42C and 43B, a scroll bar control is provided to allow the user to view other available filter terms. It will be appreciated that items may be moved into or out of the view by operations such as dragging and dropping. Each time an item is added or removed from the view, the set of specific filters provided in the filter portion 4235 is updated to account for the added or removed item.

The filter terms may be preset or dynamically generated based on evaluation of the property corresponding to the property control and the items displayed in the view. FIG. 22, described above and its accompanying description, provides an illustrative routine for dynamically generating new filter terms. The set of possible filters and their display order may depend on how the particular property categorizes the items. With a multi-valued property such as keywords, each individual value may have its own bucket. Thus, if an item has keywords “vacation; Hawaii; beach”, three separate buckets will be created, one for “vacation”, one for“Hawaii”, and one for “beach”, for filtering. The same process applies to the operations of grouping and stacking, which will be discussed further below.

For the property date, assuming today's date is Friday, Nov. 19, 2004, dates may be categorized in the following categories: Long Time Ago; Two Years Ago; Last Year; 2004 January; 2004 February; . . . ; 2004 August; 2004 September; Last Month; Three Weeks Ago; Two Weeks Ago; Last Week; Sunday; Monday; Tuesday; Wednesday; Yesterday; Today; Tomorrow; Two Days From Now; Later This Week; Later This Month; Next Year; Some Future Date. Other properties such as “Size” and “Type” may have the same bucketization as found in the Windows XP Brand Operating System.

According to one aspect, the list of filter terms in the filter portion for properties relating to dates (e.g., date created, date modified, etc.) includes an additional filtering option, which may be at the top of the list of filter terms referred to as “Pick a Date”. Selecting this filter term causes a calendar picker control to be displayed from which a user can select a specific date or date range.FIG. 45 provides an example of such a control 4500 where the date April 20 has been selected.

Certain properties may not be divided or bucketized such as Filename, Comment, Description. For these properties, there may be no useful breakdown of the property into discrete buckets for grouping, stacking and filtering purposes. In this instance, the only option presented in the arrange and filter drop down menu may be sort.

Each filter term in the arrange and filter drop down menu may include a corresponding indicator that provides an indication as to the number of items which satisfy the respective filter term. As shown in FIGS. 42C and 43B, icon 4238 is provided adjacent to the filter term “PowerPoint” and represents a stack of paper. Inspection of the other icons positioned adjacent to the other filter terms indicates that they also represent stacks of papers. However, the stack of paper icons vary in appearance and are dynamically generated, where the number of papers stacked in the icon represent, relatively, the number of items which satisfy the corresponding filter term. For example, icon 4238 shows more papers stacked then the icon corresponding to the filter term “Email Message,” which shows more papers stacked then the icon corresponding to the filter term “Outlook Document.” Thus, more items satisfy the filter term “PowerPoint” then the filter term “Email Message,” and more items satisfy the filter term “Email Message” then the filter term “Outlook Document.”

The filter portion 4235 also may include a checkbox control corresponding to each filter term in the list of filter terms. For example, the checkbox control 4240 corresponds to the filter term “Illlustrator Artwork.” Selecting the checkbox control next to a filter term causes that filter term to be added to the current selection by placing a check in the selected checkbox control, and leaves the checkbox controls corresponding to the other filter terms in the filter portion 4235 of the arrange and filter drop down menu in their previous state, selected or unselected. Also, selection of the checkbox control may show a live preview of the filter operation in the area containing the display objects. Thus, selection of the checkbox control causes the items that are represented on the display to include items that satisfy the filter term corresponding to the check box control. If no other checkbox control is selected, then only display objects which satisfy the selected checkbox control will be represented on the display. It will be appreciated that selection or de-selection of a check box control may occur in any number of ways including using a pointing device, a keyboard input, voice input, and combinations of the same. For example, if a user holds down the <SHIFT> key, she can select a range of filter terms similar to how the Windows XP brand operating system allows multiple selections.

Referring to FIGS. 42C and 43B, each display object in the display area (not shown) will satisfy the current query in the address bar (not shown) in a manner similar to described above, for example with respect to FIG. 21. Selection of the checkbox control 4240 causes the checkbox control 4240 to be presented as a checked checkbox control 4240A as shown in FIG. 42D, and causes only those items which satisfy the filter term “Illustrator Artwork” to be presented on the display. A routine similar to the routine described in FIG. 23 may be employed for selection of a checkbox control when no other checkbox control is selected, where step 922 in this scenario would correspond to a user selection of a checkbox control corresponding to one of the filter terms.

After selecting a checkbox control, selecting an <enter> command or otherwise issuing a command outside the arrange and filter drop down menu (e.g., clicking elsewhere on the graphical user interface) causes the arrange and filter drop down menu to close and applies the currently selected filter(s). Also, selecting a filter term or an icon associated with a filter term deselects any other checkbox controls, closes the arrange and filter drop down menu and applies the filter term. In these instances, the address bar (similar to address bar 641 shown in other figures such as FIG. 24) is updated to include the filter term in the query.

While a checkbox control is selected (checked), selection of another checkbox control corresponding to a second filter term adds that filter term to the current selection. Selection of the additional checkbox control causes the additional checkbox control to be presented as a checked checkbox control, and causes only those items which satisfy each of the filter terms corresponding to checked checkbox controls to be presented on the display. Referring to FIG. 44, selection of the checkbox control corresponding to the filter term “Excel Worksheet” when the checkbox control corresponding to the filter term “PDF document” has already been selected causes the display to be updated to include those items that satisfy the query in the address bar and which satisfy either the filter term “Excel Worksheet” or “PDF document.” Thus, according to this aspect of the invention, when multiple checkbox controls each corresponding to a respective filter term are selected from a single arrange and filter drop down menu then a logical OR operation is performed. As discussed, selecting an <enter> command or otherwise issuing a command outside the arrange and filter drop down menu (causes the arrange and filter drop down menu to close and applies the currently selected filters. In these instances, the query shown in the address bar is updated to include a single filter including the logical OR combination of the filter terms. For the example discussed, the filter added to the next segment in the address bar may be “Excel Worksheet, PDF document”.

De-selection of a checkbox control causes the checkbox control to be presented as unchecked, and causes those items which satisfy filter terms corresponding to the remaining checked checkbox controls to be presented on the display. When checkbox controls are selected (checked) in the arrange and filter drop down menu, each selected check box may be unchecked by selecting the command “Don't filter by <PROPERTY NAME>” in the arrangement portion of the arrange and filter drop down menu. Referring to FIG. 44, the arrangement portion 4430 of the arrange and filter drop down menu includes the command “Don't filter by Type,” selection of which will cause the selected checkbox controls in the filter portion 4435 to be deselected and unchecked. When there are no selected (checked) checkbox controls in the filter portion, the “Don't filter by <PROPERTY>” command is disabled and appears grayed out or faded as represented in the arrangement portion 4230 in FIGS. 42C and 43B.

When a user closes the arrange and filter drop down menu corresponding to a first property when at least one checkbox control is selected, the first property control may provide an indicator that the view of display objects on the display has been filtered. Referring to FIG. 43C, a symbol 4350 appears in the property control corresponding to the property “Type” to indicate that the view of display objects has been filtered by the property “Type”.

When a user closes the arrange and filter drop down menu corresponding to a first property when at least one checkbox control is selected corresponding to a respective filter term by selecting a second property control from the property header, an arrange and filter drop down menu corresponding to the second property control is provided. In this instance, the set of filter terms in the arrange and filter drop down menu is the subset of possible filter terms for which at least one item in the view satsifies the filter term for the second property control as well as the filter for the first property control. Also, the set of filter terms may include any filter that was already selected from the arrange and filter drop down menu associated with the first property control. For example, if a user were to select the checkbox control for the filter term “PowerPoint” from the arrange and filter drop down menu associated with the first property control “Type” and then select the second property control for the second property “Author” causing the arrange and filter drop down menu for “Author” to appear, the filter terms “Hamlet” and “Horatio” would both appear if “Hamlet” and “Horatio” each were an author on one or more “PowerPoint” files. However, if “Horatio” did not author any “PowerPoint” files, then “Horatio” would not appear in the arrange and filter drop down menu. If both “Horatio and “Hamlet were proper filter terms the if the checkbox control for each were then selected, the view would be updated with items that satisfied the logical operation: Type =PowerPoint AND (Author=Hamlet OR Author=Horatio). If the <enter> command were selected, the aforesaid logical operation would be applied and the address bar would be modified to include the segment “PowerPoint” followed by the segment “Hamlet, Horatio” and the view would be updated to reflect the items which satisfy the query. Generally speaking, values from different properties are combined with a logical AND operation when added to the query in the address bar.

According to another aspect, if all the property columns in the property header cannot be seen, then the columns that do not fit on the property header are truncated and may be accessed through an overflow control such as a chevron, as is common with toolbars. Selecting the chevron button displays a menu providing the truncated property controls. FIG. 44 provides an example of an arrange and filter drop down menu being activated from an overflow property control. Specifically, FIG. 44 depicts the right edge of the property header where a chevron 4450 represents that additional properties are accessible. Selection of the chevron 4450 results in the presentation of two additional property controls corresponding to the properties “Author” and “Type”. The cursor is positioned over the “Type” property control and the control corresponding to the arrange and filter drop down menu is selected presenting the arrange and filter drop down menu including an arrangment portion 4430 and a filter portion 4435.

The arrangement commands present in the arrange and filter drop down menu include “Stack by <PROPERTY>” and “Group by <PROPERTY>” as well as the “Don't Filter by <PROPERTY>” command discussed above. In the examples of the arrange and filter drop menus shown in FIGS. 42C, 43B and 44, the property is “Type.” Hence, the arrangement commands includes “Stack by Type” and “Group by Type.”

When items in view are not stacked by the property associated with arrange and filter drop down menu, the “Stack by <PROPERTY>” command is enabled. Selection of the “Stack by <PROPERTY>” command causes stacks of items to be created in the view according to the categorization applied to generate the filter terms. Thus, with respect to the property “Type”, stacks may include “Microsoft Word Documents,” “PowerPoint,” “Excel Worksheet,” and other filter terms included in the list of filter terms in the filter portion 4235 of the arrange and filter drop down menu. Illustrative stacks may take on an appearance similar to, for example, items 651-655 shown and described above in FIG. 10.

Also, a “Stop Stacking by <PROPERTY>” command may be available when items are stacked by the property of the currently activated property control. Selection of this command causes stacking by the current property to be stopped.

When items in view are not grouped by the property associated with arrange and filter drop down menu, the “Group by <PROPERTY>” command is enabled. Selection of the “Group by <PROPERTY>” command causes groups of items to be created in the view according to the categorization applied to generate the filter terms. The appearance of items grouped may be similar to grouping in the Windows XP Brand operating system. Also, a “Stop Grouping by <PROPERTY>” command may be available when items are grouped by the property of the currently activated property control. Selection of this command causes grouping by the current property to be stopped.

While illustrative systems and methods as described herein embodying various aspects of the present invention are shown, it will be understood by those skilled in the art, that the invention is not limited to these embodiments. Modifications may be made by those skilled in the art, particularly in light of the foregoing teachings. For example, each of the elements of the aforementioned embodiments may be utilized alone or in combination or subcombination with elements of the other embodiments. It will also be appreciated and understood that modifications may be made without departing from the true spirit and scope of the present invention. The description is thus to be regarded as illustrative instead of restrictive on the present invention. 

1. In a computer system having a display, a processor, and a memory for storing items with metadata properties, a graphical user interface comprising: a plurality of display objects, each display object representing one or more items; and a property header including plurality of property controls, each property control corresponding to a respective property that is shared by a plurality of the items, wherein selection of a property control causes a list of filter terms and a list of check box controls to be presented on the display, each check box control corresponding to a respective one of the filter terms, wherein the list of filter terms is dynamically generated based on evaluation of the property corresponding to the property control and the display objects, wherein selection of a first check box control causes the items that are represented on the display to only include items that satisfy a first respective filter term corresponding to the first check box control, and selection of a second check box control when the first check box control is currently selected causes the items that are represented on the display to include items that satisfy either the first respective filter term corresponding to the first check box control or a second respective filter term corresponding to the second check box control, and wherein de-selection of the second check box control causes the items that are represented on the display to include only items that satisfy at least one respective filter term corresponding to a currently selected check box control.
 2. The graphical user interface of claim 1, wherein an indicator as to the number of items which satisfy each respective filter term is presented in the list proximate to the respective filter term.
 3. The graphical user interface of claim 2, wherein the indicator is an icon which is dynamically generated.
 4. The graphical user interface of claim 3, wherein selection of the icon causes the items that are represented on the display to be filtered in accordance with the respective filter term.
 5. The graphical user interface of claim 1, wherein selection of a no filter command causes de-selection of each selected check box control.
 6. The graphical user interface of claim 1, wherein selection of a check box control causes the items that are represented on the display to satisfy the corresponding filter term and dismissing the list of filter terms causes each filter term corresponding to a selected check box control to be applied such that each item represented on the display satisfies a filter term corresponding to a selected check box.
 7. The graphical user interface of claim 1, wherein the property control is a split button including a first button portion and a second button portion, and selection of the first button portion causes the list of filter terms to be presented on the display and selection of the second button portion causes the display objects to be sorted by the property.
 8. The graphical user interface of claim 7, wherein the property control provides a visual indicator when the display objects are sorted or filtered by the property.
 9. The graphical user interface of claim 1, wherein selection of the property control causes a list of arrangement commands to be presented on the display wherein each displayed arrangement command identifies a display arrangement type, the list of arrangement commands being separated from the list of filter terms and wherein selection of an arrangement command causes the items to be rearranged on the display according to the display arrangement type of the selected arrangement command.
 10. The graphical user interface of claim 1, wherein when the property corresponding to the property control relates to a date, one of the filter terms is pick a date, and selection of the pick a date filter term causes a calendar control to be presented for a user to select a specific date or date range to filter by.
 11. The graphical user interface of claim 1, wherein the list of filter terms is presented in a drop down menu.
 12. Computer-readable media having computer-executable instructions embodied thereon that, when executed, enable a computing device to perform a method of filtering items, the method comprising: providing a plurality of display objects on the display that each represent one or more items; providing a property header including a plurality of property controls on the display, each property control corresponding to a respective property that is shared by a plurality of the items; and responsive to a user selection of a property control, causing a list of filter terms and check box controls to be presented on the display, each check box control corresponding to a respective one of the filter terms, wherein the list of filter terms is dynamically generated based on evaluation of the property corresponding to the property control and the display objects, wherein selection of a first check box control causes the items that are represented on the display to only include items that satisfy a first respective filter term corresponding to the first check box control, and selection a second check box control when the first check box control is currently selected causes the items that are represented on the display to include items that satisfy either the first respective filter term corresponding to the first check box control or a second respective filter term corresponding to the second check box control, and wherein de-selection of the second check box control causes the items that are represented on the display to include only items that satisfy at least one respective filter term corresponding to a currently selected.
 13. The media of claim 12, wherein an indicator as to the number of items which satisfy each respective filter term is presented in the list proximate to the respective filter term.
 14. The media of claim 13, wherein the indicator is an icon which is dynamically generated.
 15. The media of claim 14, wherein selection of the icon causes the items that are represented on the display to be filtered in accordance with the respective filter term.
 16. The media of claim 12, wherein selection of a no property control causes de-selection of each selected check box control.
 17. The media of claim 12, wherein dismissing the list of filter terms causes each filter term corresponding to a selected check box control to be applied such that each item represented on the display satisfies a filter term corresponding to a selected check box.
 18. The media of claim 12, wherein the property control is a split button including a first button portion and a second button portion, and selection of the first button portion causes the list of filter terms to be presented on the display and selection of the second button portion causes the display objects to be sorted by the property.
 19. The media claim 12, wherein selection of the property control causes a list of arrangement commands to be presented on the display wherein each displayed arrangement command identifies a display arrangement type, the list of arrangement commands being separated from the list of filter terms and wherein selection of an arrangement command causes the items to be rearranged on the display according to the display arrangement type of the selected arrangement command. 